Migration of full-disk encrypted virtualized storage between blade servers

ABSTRACT

A method, system and computer-readable storage medium with instructions to migrate full-disk encrypted virtual storage between blade servers. A key is obtained to perform an operation on a first blade server. The key is obtained from a virtual security hardware instance and provided to the first blade server via a secure out-of-band communication channel. The key is migrated from the first blade server to a second blade server. The key is used to perform hardware encryption of data stored on the first blade server. The data are migrated to the second blade server without decrypting the data at the first blade server, and the second blade server uses the key to access the data. Other embodiments are described and claimed.

RELATED APPLICATION

This application is a Continuation of co-pending U.S. patent application Ser. No. 12/317,945 filed Dec. 30, 2008, which is a continuation-in-part of U.S. patent application Ser. No. 11/966,136, filed Dec. 28, 2007, now abandoned, both of which are incorporated by reference herein in their entirety.

COPYRIGHT NOTICE

Contained herein is material that is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction of the patent disclosure by any person as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all rights to the copyright whatsoever.

TECHNICAL FIELD

The present disclosure relates generally to migration of data between computer systems.

BACKGROUND

Blade servers are self-contained computer servers configured for high-density computing environments. Blade servers are housed in blade enclosures, which may be configured to hold a plurality of blade servers. The plurality of blade servers and the blade enclosure form a blade server system. In a typical blade server system, each of the blade servers includes individual processors, memory, chipsets, and data storage. For example, each blade server may include one or more hard drives. During operation, each blade server stores data related to the operation of the particular blade server on its associated hard drive. As such, if a failure of one or more of the blade servers occurs, migration of the computer environment of the blade server experiencing the failure requires transfer of all the data stored on the associated hard drive to a hard drive of a replacement blade server. Such data transfer involves large amounts of data and bandwidth resulting in long data migration periods.

This migration process may be further affected when the blade server is used to store sensitive or confidential information. Sensitive or confidential information may be protected using security mechanisms such as encrypting the data and/or making use of security hardware to protect the data from unauthorized access. For example, full disk encryption (or whole disk encryption) is a kind of disk encryption (performed by either software or hardware) which encrypts every bit of data that is stored on a disk. Encryption and decryption keys are bound to the particular hardware device storing the data. Movement of data from one hardware device to another requires decryption of the data, movement of the decrypted data from one hardware device to the other, and then encryption of the data at the new hardware device. This decryption and re-encryption process further slows the migration process from one blade server to another.

A blade server may also include security hardware such as a trusted platform module (TPM). A TPM is a hardware component, typically a microcontroller, which resides within a processing system and provides various facilities and services for enhancing the security of the processing system. A TPM may be implemented in accordance with specifications such as the Trusted Computing Group (TCG) TPM Main Part 1 Design Principles Version 1.2, level 2 revision 103, dated Jul. 9, 2007 (hereinafter the “TPM specification”), which is available from the Internet at www.trustedcomputinggroup.org\home. In accordance with the TCG specification, a TPM stores an endorsement key and a storage root key internally, so that the endorsement and storage root keys are immutably bound to the platform protected by the TPM. Endorsement, storage root keys, and identity attestation keys are not migratable from one platform to another. (See TPM specification, sections 7, 7.1, 11.2, and 11.4.) As a result, the migration of data from one blade server to another is further complicated in an environment using TPM technology.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating at least one embodiment of a system to migrate data on a full disk encrypted disk volume from one blade server to another.

FIG. 2 is a flowchart describing the operation of the chassis management module of FIG. 1 in managing blade servers and providing functionality for migrating full-disk encrypted virtualized storage from one blade server to another.

FIG. 3 is a flowchart describing the operation of the chassis management module of FIG. 1 in processing a security hardware command.

FIG. 4 is a flowchart describing the operation of the chassis management module of FIG. 1 in processing a migration event among blade servers protected by security hardware and full disk encryption.

FIG. 5 is a flowchart describing the operation of the platform controller of FIG. 1 in processing a security hardware command.

DETAILED DESCRIPTION

In general, a TCG-compliant TPM stores keys, passwords, and digital certificates securely. A TPM uses several types of keys, including identity keys to certify data; signing keys to sign data; storage keys to protect sensitive data including key material; and binding keys used to bind and protect sensitive data. A TPM attests to the identity and/or integrity of the platform, based on characteristics such as hardware components of the platform, including the processor(s) and chipset, as well as the software residing in the platform, such as the firmware and operating system. A TPM may also support auditing and logging of software processes, as well as verification of platform boot integrity, file integrity, and software licensing. A TPM is often described as providing a root of trust for a platform. However, as mentioned above, the endorsement key, storage root key, and identity attestation keys for a TPM are stored within the TPM, are immutably bound to the platform protected by the TPM, and thus are not migratable from one blade server to another.

Referring now to FIG. 1, a blade server system 100 includes a blade server enclosure 102 and a plurality of blade servers 104 (shown as individual blade servers 104 a-104 n) housed in the blade server enclosure 102. The blade server enclosure 102 may be configured to support various numbers of blade servers 104. For example, the blade server enclosure 102 may be configured to house twenty, forty, one hundred, or more blade servers 104. To do so, the blade server enclosure 102 may include structural components such as guide rails or the like (not shown) to provide a slot or port for securing each of the blade servers 104 to the enclosure 102.

The blade server system 100 also includes a chassis management module (CMM) 106 and a shared data storage device 108 such as a hard drive. In the illustrative embodiment of FIG. 1, the chassis management module 106 and the storage device 108 are housed in the blade server enclosure 102. However, in other embodiments, the chassis management module 106 and the storage device 108 may be external or otherwise remote relative to the blade server enclosure 102. For example, the storage device 108 may be embodied as a remote hard drive, and/or the chassis management module 106 may be an external computer system connected via a secure network connection (not shown) to blade server system 100.

In the illustrative embodiment, the chassis management module 106 includes a processor 110 and a memory device 112. The processor 110 illustratively includes a single processor core (not shown). However, in other embodiments, the processor 110 may be embodied as a multi-core processor having any number of processor cores. Additionally, chassis management module 106 may include additional processors having one or more processor cores in other embodiments. The memory device 112 may be embodied as dynamic random access memory devices (DRAM), synchronous dynamic random access memory devices (SDRAM), double-data rate dynamic random access memory device (DDR SDRAM), and/or other volatile memory devices. Additionally, although only a single memory device is illustrated in FIG. 1, in other embodiments, the chassis management module 106 may include additional memory devices.

Processor 110 is shown as including a plurality of virtual security hardware instances 111 (with individual virtual security hardware instances 111 a-111 n). Each of virtual security hardware instances 111 a-111 n emulates the security features offered by a physical TPM to store keys, passwords, and digital certificates securely, but is not bound to the platform as a physical TPM would be bound to the platform. Virtual security hardware instances 111 can be emulated using a combination of hardware and software or in software only. Each virtual security hardware instance 111 a-111 n may be associated with a particular one of blade servers 104 (individually shown as blade servers 104 a-104 n) within blade enclosure 102. Because the keys associated with virtual security hardware instances 111 are not bound to particular hardware devices, the keys associated with virtual security hardware instances 111 are migratable from one blade server to another within blade servers 104.

Chassis management module 106 may include other components, sub-components, and devices not illustrated in FIG. 1 for clarity of the description. For example, it should be appreciated that the chassis management module 106 may include a chipset, input/output ports and interfaces, network controllers, and/or other components.

The chassis management module 106 is communicatively coupled to the blade servers 104 via a plurality of signal paths 114. The signal paths 114 may be embodied as any type of signal paths capable of facilitating communication between the chassis management module 106 and the individual blade servers 104. For example, the signal paths 114 may be embodied as any number of interfaces, buses, wires, printed circuit board traces, via, bus, intervening devices, and/or the like. Signal paths 114 are also referred to as an out-of-band communication channel 114 with reference to blade servers 104. The “out-of-band” description is used because signal paths 114 are not accessible via an external network, such as by connecting to one of blade servers 104 via a network interface controller within the blade server. If the chassis management module 106 is not housed inside blade server enclosure 102, signal paths 114 may be embodied as one or more secure network communication links that do not allow external network connections to individual blade servers 104 a-104 n.

As discussed above, the shared data storage may be embodied as any type of storage device capable of storing data from each of the blade servers 104. For example, in the embodiment illustrated in FIG. 1, the shared data storage device 108 is embodied as a hard drive having a plurality of virtual partitions 116 (with individual virtual partitions shown as 116 a-116 n). Each of the blade servers 104 is associated with one of the virtual partitions 116 and configured to store data within the associated virtual partition 116 during operation as discussed in more detail below. Because each of the blade servers 104 also has a respective virtual security hardware instance 111 a-111 n, data associated with the virtual security hardware instances 116 a-116 n may also be stored in the respective virtual partitions 116 a-116 n. The shared data storage 108 is communicatively coupled to each of the blade servers 104 via a plurality of signal paths 118. Similar to signal paths 114, the signal paths 118 may be embodied as any type of signal paths capable of facilitating communication between the shared data storage 108 and the individual blade servers 104. For example, the signal paths 118 may be embodied as any number of interfaces, buses, wires, printed circuit board traces, via, bus, intervening devices, and/or the like. If shared data storage 108 is external to blade server enclosure 102, then signal paths 118 may include one or more secure network communication links.

Each of the blade servers 104 includes a processor 120, a chipset 122, and a memory device 124. The processor 120 illustratively includes a single processor core (not shown). However, in other embodiments, the processor 120 may be embodied as a multi-core processor having any number of processor cores. Additionally, each of blade servers 104 may include additional processors having one or more processor cores in other embodiments. The processor 120 is communicatively coupled to the chipset 122 via a plurality of signal paths 128. The signal paths 128 may be embodied as any type of signal paths capable of facilitating communication between the processor 120 and the chipset 122 such as any number of interfaces, buses, wires, printed circuit board traces, via, bus, intervening devices, and/or the like.

The memory device 124 may be embodied as dynamic random access memory devices (DRAM), synchronous dynamic random access memory devices (SDRAM), double-data rate dynamic random access memory device (DDR SDRAM), and/or other volatile memory devices. Additionally, although only a single memory device is illustrated in FIG. 1, in other embodiments, each blade server 104 may include additional memory devices. The memory 124 is communicatively coupled to the chipset 122 via a plurality of signal paths 130. Similar to the signal paths 128, the signal paths 130 may be embodied as any type of signal paths capable of facilitating communication between the chipset 122 and the memory 124 such as any number of interfaces, buses, wires, printed circuit board traces, via, bus, intervening devices, and/or the like.

Each of blade servers 104 may also include other devices such as various peripheral devices. For example, as illustrated in FIG. 1, each of the blade servers 104 may include an individual hard drive 126 or other peripheral device. Hard drive 126 is representative of any type of data storage for blade servers 104, including locally attached SAS (serial attached storage), Internet SCSI-network attached or Infiniband attached storage. Data stored on hard drive 126 may be protected using full disk encryption. Additionally, it should be appreciated that each of blade servers 104 may include other components, sub-components, and devices not illustrated in FIG. 1 for clarity of the description. For example, it should be appreciated that the chipset 122 of each of blade servers 104 may include a memory controller hub (MCH) or northbridge, an input/output controller hub (ICH) or southbridge, a baseboard management controller (BMC) for out-of-band management of platform hardware, and/or other devices.

Each of blade servers 104 also includes a platform controller 123. Platform controller 123 provides logic to manage an out-of-band interface between chassis management module 106 and platform hardware. For example, platform controller 123 may be provided by a Baseboard Management Controller (BMC) in accordance with the Intelligent Platform Management Interface (IPMI) architecture. An out-of-band interface such as IPMI operates independently of an operating system ((OS), not shown in FIG. 1) running on processor 120 and allows an administrator using chassis management module 106 or other system management software to manage the entire blade server enclosure 102 even in the absence of an operational operating system on one or more of the individual blade servers 104 a-104 n. Platform controller 123 is communicatively coupled to chassis management module 106 by signal paths 114, which may serve as an out-of-band communication channel with respect to blade servers 104. Out-of-band communication channel 114 enables chassis management module 106 to communicate directly with platform hardware.

In one embodiment, platform controller 123 provides a TPM Interface Specification (TIS) interface 125 in conformance with the TCG's TPM Interface Specification such that software running on a blade server such as blade server 104 a functions as if blade server 104 a were protected by security hardware such as a TPM. TIS interface 125 may provide, for example, memory-mapped I/O registers in conformance with the TCG's TPM Interface Specification. Rather than provide the TPM functionality in a hardware component on each of blade servers 104, however, in one embodiment TPM commands issued by host software on a given blade server such as blade server 104 a are sent by platform controller 123 via out-of-band communication channel 114 to chassis management module 106.

In one embodiment, platform controller 123 and TIS interface 125 functionality are provided by Intel's Management Engine integrated TPM (iTPM) as provided in the Intel ICH10 platform controller hub.

Chassis management module 106 acts on the TPM (or other security hardware) commands issued by host software on the blade servers 104, providing security functionality such as encryption and decryption keys to the blade servers 104. For example, each of blade servers 104 may include host software such as Microsoft Windows Server 2008 operating system with the BitLocker feature to provide security in the form of full disk encryption to data stored on blade servers 104. TPM (or other security hardware) commands issued by the Server 2008 operating system instance running on a particular blade server such as blade server 104 a are processed by chassis management module 106. The operation of chassis management module 106 is described in further detail with reference to FIG. 2.

Referring again to FIG. 1, each of the blade servers 104 is configured to store environment data on the shared data storage device 108 in one of the associated virtual partitions 116 (individually shown as virtual partitions 116 a-116 n). The data stored on shared storage device 108 includes data necessary to reconstruct the computing environment, such as processor state information and register contents for the computing environment. If a migration event occurs, such as a failure of one of the blade servers such as blade server 104 a, the chassis management module 106 migrates the computing environment, such as a virtual machine, of the failing blade server 104 a to a new blade server, such as blade server 104 n. Because each of the blade servers 104 uses a shared storage space (e.g., a shared hard drive), the computing environment of the failing blade server 104 a may be migrated without the need to transfer the large amount of data stored on the shared data storage device 108. Rather, the logical unit number (LUN) associated with the virtual partition used by the failing blade server 104 a, such as the logical unit for virtual partition 116 a, may be transferred to the new, replacement blade server 104 n. Additionally, the state of the processor 120 of the failing blade server 104 a may be transferred to the replacement blade server 104 n.

FIG. 2 describes the operation of chassis management module 106 of FIG. 1 in managing blade servers and providing functionality for migrating full-disk encrypted virtualized storage from one blade server to another. In “System Initialization” step 202, system initialization is performed. For example, the chassis management module 106 and each of the blade servers 104 are initialized in block 202. The steps involved in initial configuration of an individual blade server are described in further detail with reference to FIG. 2 steps 208 through 212.

After “System Initialization” step 220, chassis management module 106 transitions to “Continue System Operations” step 204. In “Continue System Operations” step 204, the blade server system 100 continues normal operation. That is, each of the blade servers 104 continues normal operation, which may, for example, include processing data, storing data, and establishing one or more virtual machines. During operation, each of the blade servers 104 is configured to store environment data, such as data related to the state of operation of the respective blade server, in the shared data storage device 108 (e.g., a hard drive) as indicated in block 206. This environment data stored on shared data storage device 108 is in addition to application-level data stored by a blade server such as blade server 104 a on its respective hard drive 126. The application-level data stored on the respective hard drives 126 may be protected by full disk encryption.

One or more of the virtual partitions 116 may be assigned to one of the blade servers 104 and/or one or more virtual machines established on one of the blade servers 104. The location of the respective virtual partition 116 a-116 n on the shared data storage device 108 is identified by a logical unit number (LUN). As such, each of blade servers 104 and/or each virtual machine established on each of blade servers 104 may be configured to store data related to that blade server's computing environment in an associated one of the virtual partitions 116 of the data storage device 108 based on an assigned logical unit number.

Referring again to FIG. 2, at “Blade Configuration Request?” decision point 208, the chassis management module 106 of the blade server system 100 monitors for a blade configuration request. A blade configuration request may be generated when a new blade server 104 is coupled to the blade server system 100 or is otherwise rebooted or initialized (as described above with reference to “System Initialization” step 202). If a blade configuration request is received, chassis management module 106 transitions to “Map OS Loader and Kernel Images to Server Memory” step 210, where an operating system loader and kernel images are mapped to the memory 124 of one of the blade servers 104. Chassis management module 106 causes the BIOS for a given blade server such as blade server 104 a to invoke the operating system loader, which in turn loads an operating system instance such as a Microsoft Windows Server 2008 operating system instance. When the operating system and kernel images have been loaded to the blade server memory 124, chassis management module 106 transitions to “Act as a Boot Server Providing Boot Images and Provisioning Information” step 412, where chassis management module 106 acts as a boot server to the new blade server such as blade server 104 a and provides boot images and provisioning information to the requesting blade server 104 a. Upon completion of “Act as a Boot Server Providing Boot Images and Provisioning Information” step 412, chassis management module 106 returns to “Continue System Operations” step 204 of FIG. 2.

In addition to monitoring for blade configuration requests, chassis management module 106 monitors for security hardware commands at “Receive Security Hardware Command” decision point 220. An example of one type of security hardware command is a “take ownership” command where a given blade server's operating system requests to take ownership of associated security hardware. These security hardware commands may be received, for example, via out-of-band communication channel 114 from platform controller 123 as described above with reference to FIG. 1. The actions of platform controller 123 in processing these security hardware commands are described in further detail with reference to FIG. 5.

Referring again to FIG. 2, when a security hardware command is received, chassis management module 106 transitions to “Process Security Hardware Command” step 222. “Process Security Hardware Command” step 222 is discussed in further detail with reference to FIG. 3.

Referring again to FIG. 2, in addition to monitoring for blade configuration requests and security hardware commands, chassis management module 106 monitors for a migration event at “Migration Event” decision point 230. The migration event may be embodied as any one of a number of events that prompt the migration of a computing environment such as a virtual machine from one blade server such as blade server 104 a to another blade server such as blade server 104 n. For example, in some embodiments, the migration event may be defined by failure of blade server 104 a or devices or components of the blade server 104 a. Additionally or alternatively, the migration event may be based on load balancing or optimization considerations. For example, the chassis management module 106 may be configured to monitor the load of each of the blade servers 104. Chassis management module 106 may migrate virtual machines or other computing environments from those blade servers 104 having excessive loads to other blade servers 104 having loads of lesser value such that the total load is balanced or otherwise optimized across the plurality of blade servers 104.

Additionally or alternatively, a migration event may be based on a predicted failure. For example, chassis management module 106 may be configured to monitor the power consumption, temperature, or other attribute of each of blade servers 104. The chassis management module 106 may further be configured to determine the occurrence of a migration event when the power consumption, temperature, or other attribute of one of blade servers 104 is above some predetermined threshold, which may be indicative of a future failure of that particular blade server. Such power consumption, temperature, and other attributes may be monitored over a period of time and averaged to avoid false positives of migration events due to transient events such as temperature spikes.

Upon detection of a migration event at “Migration Event” decision point 230, chassis management module 106 transitions to “Process Migration Event” step 232. “Process Migration Event” step 232 is discussed in further detail with reference to FIG. 4.

It should be appreciated that the chassis management module 106 may monitor for blade configuration requests, security hardware commands, and migration events in a contemporaneous, near contemporaneous, or sequential manner. That is, in FIG. 2, decision points 208, 220, and 230 may be executed by the chassis management module 106 or other component of the blade server system 100 contemporaneously with each other or sequentially in a predefined order.

Referring to FIG. 3, an algorithm for processing security hardware commands by chassis management module 106 is provided. Chassis management module 106 acts on hardware security commands, such as TPM commands, issued by host software on the blade servers 104, providing security functionality including encryption and decryption keys to the blade servers 104.

For example, if chassis management module 106 determines that a blade server's operating system has requested to take ownership of security hardware for the blade server, chassis management module 106 creates a virtual security hardware instance, such as one of virtual security hardware instances 111 a-111 n, to emulate the security hardware for the requesting blade server. The operating system for the blade server functions as if physical security hardware were available for the blade server, but the security hardware is instead emulated by chassis management module 106. This emulation enables the blade server operating system to operate without modification as if security hardware were present, while still providing the blade server with equivalent security protection. In response to the take ownership command, chassis management module 106 emulates the security hardware by creating a virtual security hardware instance, such as one of virtual security hardware instances 111 a-111 n, for the requesting blade server.

In processing a security hardware command, chassis management module 106 begins at “Does Virtual Security Hardware Instance Exist for Requesting Blade Server?” decision point 310. If no virtual security hardware instance exists for the requesting blade server, control transitions to “Create Virtual Security Hardware Instance for Requesting Blade Server” step 320. Alternatively, if a virtual security hardware instance has already been created for the requesting blade server, control transitions to “Identify Virtual Security Hardware Instance for Requesting Blade Server” step 330.

At “Create Virtual Security Hardware Instance for Requesting Blade Server” step 320, chassis management module 106 creates a virtual security hardware instance, such as one of virtual security hardware instances 111 a-111 n, to provide security protection that otherwise would be provided by physical security hardware on the blade server. This security protection may be implemented by the virtual security hardware instance using one or more security hardware components such as TPMs under the control of the chassis management module 106. Alternatively, the virtual security hardware instance may provide security protection as a logical device. An example implementation of providing a virtual security hardware instance as a logical device is described in pending patent application Ser. No. 10/876,994, entitled “Method and Apparatus for Providing Secure Virtualization of a Trusted Platform Module,” which is assigned to the assignee of the present application and is incorporated by reference in its entirety herein.

Providing security protection of blade servers 104 by chassis management module 106 is more secure than having a physical security hardware device on each of the blade servers because the physical and/or logical devices managed by chassis management module 106 are separated from the blade servers 104 by an out-of-band communication channel such as out-of-band communication channel 114. Tampering with the security protection of blade servers 104 would require compromising not only one of the blade servers 104 but also the communication occurring via out-of-band communication channel 114 with the chassis management module 106.

At “Identify Virtual Security Hardware Instance for Requesting Blade Server” step 330, the virtual security hardware instance for the requesting blade server is identified by chassis management module 106. Chassis management module 106 may look up the associated virtual security hardware instance in a table stored in memory 112. The virtual security hardware instance may be identified, for example, using a key provided with the security hardware command.

When the virtual security hardware instance for the requesting blade server is created or identified at respective “Create Virtual Security Hardware Instance for Requesting Blade Server” step 320 or “Identify Virtual Security Hardware Instance for Requesting Blade Server” step 330, chassis management module 106 transitions to “Obtain Appropriate Key from Virtual Security Hardware Instance for Requesting Blade Server” step 340. Depending upon the security hardware command, a different type of key may be obtained. For example, chassis management module 106 may provide a storage root key for the associated virtual security hardware instance in response to a “take ownership” command, an encryption key in response to a request to create an encryption key, and so on. The virtual security hardware instance provides a key as if a physical TPM were present to provide the key for the requesting blade server.

From “Obtain Appropriate Key from Virtual Security Hardware Instance for Requesting Blade Server” step 340, chassis management module 106 transitions to “Provide Key to Sender of Command” step 350. Chassis management module 106 provides the key via out-of-band communication channel 114 to platform controller 123 for the requesting blade server. The operation of platform controller 123 is described in further detail with reference to FIG. 5.

Referring to FIG. 4, the operation of chassis management module 106 is described in processing a migration event among blade servers protected by security hardware and full disk encryption. During a migration event, the computing environment (e.g., one or more virtual machines) is migrated from one blade server, described herein as the source blade server, to another blade server, described herein as the destination blade server. For example, if the chassis management module 106 determines that a blade server such as blade server 104 a has failed, will likely fail, or is over loaded, chassis management module 106 may migrate the computing environment such as one or more virtual machines from the source blade server 104 a to a destination blade server such as blade server 104 n. The destination blade server may be a new blade server or a pre-existing blade server operating at less than full capacity.

To migrate data from one blade server to another in an environment protected by security hardware and full disk encryption, chassis management module 106 begins at “Identify and/or Create Virtual Security Hardware Instances for Source Blade Server and Destination Blade Server” step 410. If a new blade server has been added to provide the destination blade server, a corresponding virtual security hardware instance may need to be created as previously described with reference to “Create Virtual Security Hardware Instance for Requesting Blade Server” step 320 of FIG. 3. Otherwise, chassis management module 106 identifies the virtual security hardware instances for the source and destination blade servers. Chassis management module 106 then transitions to “Provide Storage Root Key for Source Blade Server to Virtual Security Hardware Instance for Destination Blade Server as Part of Environment State” step 420. In one embodiment, the entire state of the virtual security hardware instance (such as the entire state of all memory variables associated with one of virtual security hardware instances 111 a-111 n including the storage root key), is copied from the source virtual security hardware instance to the destination security hardware instance. This state information is copied from one virtual security hardware instance to another, such as from virtual security hardware instance 111 a associated with blade server 104 a to virtual security hardware instance 111 n associated with blade server 104 n within chassis management module 106. In addition, the state information may be copied from one virtual partition to another for the associated blade servers, such as from virtual partition 116 a associated with blade server 104 a to virtual partition 116 n associated with blade server 104 n.

To migrate the computing environment of one blade server 104 a to another blade server 104 n, chassis management module 106 then transitions to “Switch LUN to Destination Blade Server and Migrate Environment State from Source Blade Server to Destination Blade Server” step 430. In this step, chassis management module 106 switches or otherwise transfers the logical unit number (LUN) used by the source blade server 104 a, which identifies one of the virtual partitions 116 such as virtual partition 116 a associated with source blade server 104 a, to the destination blade server 104 n. This transfer of the LUN from one blade server to another occurs by copying data from one virtual partition to another. As a result, the destination blade server 104 n will have access to all of the environment data used by and stored by the first blade server 104 a in the associated virtual partition 116 a. In addition, chassis management module 106 may transfer the state of the central processing unit or processor 120 of the source blade server 104 a to the destination blade server 104 n. For example, the chassis management module 106 may copy the data contained in the software registers of the source blade server 104 a to the software registers of the destination blade server 104 n. In addition, the LUN may be copied from virtual security hardware instance 116 a associated with blade server 104 a to the virtual security hardware instance 116 n associated with blade server 104 n.

Additional data or state information, such as a storage root key for the virtual security hardware instance for source blade server 104 a may be transferred from the source blade server 104 a to the destination blade server 104 n. The entire state of the virtual security hardware instance for source blade server 104 a may be transferred to a respective virtual partition, such as virtual partition 116 n, to accomplish the migration. By transferring a storage root key from one virtual security hardware instance to another, the destination blade server obtains access to all of the data encrypted by hardware at the first blade server without the need to decrypt the data prior to migration. This technique effectively extends the concept of the TCG “Trusted Building Block” associated with a TPM from a single blade server to a chassis management module in combination with a blade server. The concept of the platform associated with a TPM is similarly extended to a chassis management module in combination with a blade server. By extending the concept of the platform to a chassis management module in combination with a blade server, a storage root key for the platform can be migrated from one blade server to another.

It should be appreciated that because the environment data used by a given blade server such as blade server 104 a is not transmitted (e.g., transmitted by means of an Ethernet connection from one blade server to another), the security of the environment data used by source blade server 104 a is increased. That is, the data used by the source blade server 104 a to manage the computing environment is effectively transferred to the destination blade server 104 n via the transfer of the logic unit number rather than the transfer of the actual environment data. As such, the “transferred” environment data remains stored on the shared data storage device 108.

Referring to FIG. 5, a flowchart shows the operation of an embodiment of the platform controller 123 of FIG. 1 in processing a security hardware command. As described with reference to FIG. 1, platform controller 123 may provide a TIS interface 125 in conformance with the TCG's TPM Interface Specification such that software running on a blade server such as blade server 104 a functions as if blade server 104 a were protected by security hardware such as a TPM. TIS interface 125 may provide, for example, memory-mapped I/O registers in conformance with the TCG's TPM Interface Specification. Rather than provide the TPM functionality in a hardware component on each of blade servers 104, however, in one embodiment TPM commands issued by host software on a given blade server such as blade server 104 a are sent by platform controller 123 via out-of-band communication channel 114 to chassis management module 106.

Referring to FIG. 5, at “Intercept Security Hardware Command from Blade Server Software” step 510, platform controller 123 intercepts the security hardware command sent by software running on a blade server such as blade server 104 a via TIS interface 125. Platform controller 123 transitions to “Send Command to Chassis Management Module (CMM) via Secure Out-of-Band Communication Channel” step 520, where platform controller 123 sends the security hardware command to chassis management module 106 via a secure out-of-band communication channel such as out-of-band communication channel 114 of FIG. 1. Control then transitions to “Receive Key to Perform Command from CMM” step 530, where platform controller 123 receives the key via secure out-of-band communication channel 114 from chassis management module 106. Platform controller 123 then transitions to “Provide Key to Requesting Blade Server” step 540, where platform controller 123 provides the key via TIS interface 125 to the blade server software that issued the command intercepted at “Intercept Security Hardware Command from Blade Server Software” step 510. The blade server software then uses the key to perform the command. For example, blade server software such as Microsoft Server 2008 may use the BitLocker feature to use a storage root key provided by chassis management module 106 to encrypt or decrypt data stored on blade server 104 a.

Embodiments of the mechanisms disclosed herein may be implemented in hardware, software, firmware, or a combination of such implementation approaches. Embodiments of the invention may be implemented as computer programs executing on programmable systems comprising at least one processor, a data storage system (including volatile and non-volatile memory and/or storage elements), at least one input device, and at least one output device.

Program code, such as code to implement the algorithms shown in the flowcharts of FIGS. 2-5, may be applied to input data to perform the functions described herein and generate output information. For example, this program code may include firmware for a microcontroller encoded to perform embodiments of the methods shown in FIGS. 2-5. Accordingly, embodiments of the invention also include machine-accessible media containing instructions for performing the operations of the invention or containing design data, such as HDL, which defines structures, circuits, apparatuses, processors and/or system features described herein. Such embodiments may also be referred to as program products.

Such machine-accessible storage media may include, without limitation, tangible arrangements of particles manufactured or formed by a machine or device, including storage media such as hard disks, any other type of disk including floppy disks, optical disks, compact disk read-only memories (CD-ROMs), compact disk rewritable's (CD-RWs), and magneto-optical disks, semiconductor devices such as read-only memories (ROMs), random access memories (RAMs) such as dynamic random access memories (DRAMs), static random access memories (SRAMs), erasable programmable read-only memories (EPROMs), flash memories, electrically erasable programmable read-only memories (EEPROMs), magnetic or optical cards, or any other type of media suitable for storing electronic instructions.

The output information may be applied to one or more output devices, in known fashion. For purposes of this application, a processing system includes any system that has a processor, such as, for example; a digital signal processor (DSP), a microcontroller, an application specific integrated circuit (ASIC), or a microprocessor.

The programs may be implemented in a high level procedural or object oriented programming language to communicate with a processing system. The programs may also be implemented in assembly or machine language, if desired. In fact, the mechanisms described herein are not limited in scope to any particular programming language. In any case, the language may be a compiled or interpreted language.

Presented herein are embodiments of methods and systems for enabling migration of full disk encrypted data between blade servers. While particular embodiments of the present invention have been shown and described, it will be obvious to those skilled in the art that numerous changes, variations and modifications can be made without departing from the scope of the appended claims. Accordingly, one of skill in the art will recognize that changes and modifications can be made without departing from the present invention in its broader aspects. The appended claims are to encompass within their scope all such changes, variations, and modifications that fall within the true scope and spirit of the present invention. 

What is claimed is:
 1. A system, comprising: a plurality of blade servers; and a chassis management module; wherein each of the plurality of blade servers comprises a platform controller configured to manage an out-of-band interface between the chassis management module and a the plurality of blade servers.
 2. The system of claim 1, wherein the platform controller comprises a baseboard management controller.
 3. The system of claim 1, wherein each of the plurality of blade servers comprises a processor to execute an operating system, and the out-of-band interface is configured to operate independently of the execution of said operating system.
 4. The system of claim 3, wherein the out-of-band interface is configured to enable an administrator to manage the operation of the plurality of blade servers even in the absence of an operational operating system on one or more of the plurality of blade servers.
 5. The system of claim 1, further comprising an out-of-band communication channel, the out-of-band communication channel configured to enable the chassis management module to communicate directly with the platform controller.
 6. The system of claim 1, wherein the out-of-band interface is a trusted platform module interface in conformance with a trusted platform module interface specification.
 7. The system of claim 1, wherein the out-of-band interface is configured to cause software executing on a first blade server of the plurality of blade servers to function as though the first blade server was protected by security hardware.
 8. The system of claim 7, wherein the out-of-band interface is configured to provide memory-mapped input/output registers in conformance with a trusted platform module interface specification.
 9. The system of claim 7, wherein said platform controller is further configured to send a security command to said chassis management module via an out-of-band communication channel, the security command configured to cause the chassis management module to provide security functionality to the plurality of blade servers.
 10. A method comprising, managing, with a platform controller of a system further comprising a plurality of blade servers and a chassis management module, an out-of-band interface between the chassis management module and the plurality of blade servers.
 11. The method of claim 10, wherein the platform controller comprises a baseboard management controller.
 12. The method of claim 10, wherein: each of the plurality of blade servers comprises a processor to execute an operating system; the out-of-band interface is configured to operate independently of the execution of said operating system; and the method further comprises managing the operation of the plurality of blade servers with the chassis management module even in the absence of an operational operating system on one of more of the plurality of blade servers.
 13. The method of claim 10, further comprising: with an out-of-band communication channel, enabling the chassis management module to communicate directly with the platform controller.
 14. The method of claim 10, wherein the out-of-band interface is a trusted platform module interface in conformance with a trusted platform module interface specification.
 15. The method of claim 10, further comprising, with the out-of-band interface: enabling software executing on a first blade server of the plurality of blade servers to function as though the first blade server was protected by security hardware.
 16. The method of claim 15, wherein said enabling comprises providing, with the out-of-band interface, memory-mapped input/output registers in conformance with a trusted platform module interface specification.
 17. The method of claim 15, further comprising: transmitting, with said platform controller, a security command to said chassis management module via an out-of-band communication channel, the security command configured to cause the chassis management module to provide security functionality to the plurality of blade servers.
 18. At least one computer readable medium comprising computer readable instructions which when executed by a processor result in the performance of the following operations comprising: managing, with a platform controller of a system further comprising a plurality of blade servers and a chassis management module, an out-of-band interface between the chassis management module and the plurality of blade servers.
 19. The at least one computer readable medium of claim 18, wherein the platform controller comprises a baseboard management controller.
 20. The at least one computer readable medium of claim 18, wherein: each of the plurality of blade servers comprises a processor to execute an operating system; the out-of-band interface is configured to operate independently of the execution of said operating system; and said instructions when executed further result in the performance of the following operations comprising: managing the operation of the plurality of blade servers with the chassis management module even in the absence of an operational operating system on one of more of the plurality of blade servers.
 21. The at least one computer readable medium of claim 18, wherein said instructions when executed further result in the performance of the following operations comprising: with an out-of-band communication channel, enabling the chassis management module to communicate directly with the platform controller.
 22. The at least one computer readable medium of claim 18, wherein the out-of-band interface is a trusted platform module interface in conformance with a trusted platform module interface specification.
 23. The at least one computer readable medium of claim 18, wherein said instructions when executed further result in the performance of the following operations comprising: enabling, with the out-of-band interface, software executing on a first blade server of the plurality of blade servers to function as though the first blade server was protected by security hardware.
 24. The at least one computer readable medium of claim 23, wherein said enabling comprises providing, with the out-of-band interface, memory-mapped input/output registers in conformance with a trusted platform module interface specification.
 25. The at least one computer readable medium of claim 23, wherein said instructions when executed further result in the performance of the following operations comprising: transmitting, with said platform controller, a security command to said chassis management module via an out-of-band communication channel, the security command configured to cause the chassis management module to provide security functionality to the plurality of blade servers. 